Skip to content

fix: Attachables destroy order of operations#3931

Draft
NoelStephensUnity wants to merge 1 commit intodevelop-2.0.0from
fix/attachablebehaviours-despawn-errors-scene-changes
Draft

fix: Attachables destroy order of operations#3931
NoelStephensUnity wants to merge 1 commit intodevelop-2.0.0from
fix/attachablebehaviours-despawn-errors-scene-changes

Conversation

@NoelStephensUnity
Copy link
Copy Markdown
Member

Purpose of this PR

Fixing some issues based on varying destroy order of operations (more recent change where instantiation order does not reflect the order in which they will be destroyed via SceneManager during an in-session scene load (single mode).

Jira ticket

(WIP)

Changelog

  • Fixed: Issue where either an AttachableBehaviour or an AttachableNode can throw an exception if there are still attached objects when a new, in-session, scene is loaded in single mode.

Documentation

  • No documentation changes or additions were necessary. (TBD)

Testing & QA (How your changes can be verified during release Playtest)

Functional Testing

Manual testing :

  • Manual testing done

Automated tests:

  • Covered by existing automated tests
  • Covered by new automated tests (WIP)

Does the change require QA team to:

  • Review automated tests?
  • Execute manual tests?
  • Provide feedback about the PR?

If any boxes above are checked the QA team will be automatically added as a PR reviewer.

Backports

This is v2.x.x. specific.

Fixing some issues based on varying destroy order of operations (more recent change where instantiation order does not reflect the order in which they will be destroyed via SceneManager during an in-session scene load (single mode).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant